creeping featurism

creeping featurism
The tendency for complex systems to become even more complex over time due to the constant addition of new features.
Example Citations:
Features sell. Long ago, Microsoft recognized that features sell software not code size, efficiency, or even a pretty interface. Features. In the old days of software competition, to compete with Microsoft, you would put up a features chart and a side by side comparison of your product to the Microsoft offering. When your product was faster, you'd sell speed as a feature. Microsoft would counter by copying the same features and combining them with those of another competitor's product. Nobody could match Microsoft for adding features. And when Microsoft couldn't add features, it would say it added them and just not implement them, knowing people were buying software based on the claimed features, not on any real usefulness of these features.
In the 1980s, the term creeping featurism was coined. It's now become part of the landscape.
— John C. Dvorak, "Microsoft, Innovation, and Linux," PC Magazine, January 1, 2003
The tendency for fancy software add-ons, called "creeping featurism", is also a hidden menace. The more functions a program boasts, the harder it is for a user to find the one he or she needs.
— Anjana Ahuja, "A price we must pay for progress," The Times, June 18, 1997
Earliest Citation:
Since mainframes have been around longer, the software development process has been fairly well defined.
On the other hand, micro software is often written on the fly. For micros, "the process used in development is pretty crude," Miller said.
He calls the phenomenon "creeping featurism." The program's originators start out with one objective and end up tacking on more features as the program is written.
— Avery Jenkins, "In search of PC software standards," PC Week, October 23, 1984
Related Words: Category:
The term "creeping featurism" was used in a 1976 Programmer's Workbench paper I wrote, and in a talk first done in 1977, and later gave (as an ACM National Lecture) about 50-70 times through 1982. The original foils were scanned in 2002, and the phrase is used on Slide 033 within the talk.
I've lost the cartoon pair that went with this: the first, a smiling little innocent baby feature, the second, the monstrous tentacled adult creature.
I can't recall if I actually coined this myself or heard it somewhere, but in any case, the phrase was certainly in public use by 1976.
Article: Abstract:
"In line with the philosophy of much existing UNIX software, an attempt has been made to add new features only when they are shown necessary by actual user experience in order to avoid contaminating a compact, elegant system through “creeping featurism.”"

New words. 2013.

Игры ⚽ Поможем написать курсовую

Look at other dictionaries:

  • Creeping elegance — Creeping elegance, related to creeping featurism and second system effect, is the tendency of programmers to disproportionately emphasize elegance in software at the expense of other requirements such as functionality, shipping schedule, and… …   Wikipedia

  • Software bloat — Software bloat, also known as bloatware or elephantware [ [ 5 most annoying programs on your pc/ The 5 most annoying programs on your PC Download Squad ] ] , is a term used in both a neutral and… …   Wikipedia

  • Feature creep — For the project management concept, see scope creep. Feature creep, creeping featurism or featureitis is the ongoing expansion or addition of new features in a product, such as in computer software.[1] Extra features go beyond the basic function… …   Wikipedia

  • Ergonomics — Ergonomics: the science of designing user interaction with equipment and workplaces to fit the user. Ergonomics is the study of designing equipment and devices that fit the human body, its movements, and its cognitive abilities. The International …   Wikipedia

  • Editor war — For a type of conflict between wiki editors, see Edit war. Editor war is the common name for the rivalry between users of the vi and Emacs text editors. The rivalry has become a lasting part of hacker culture and the free software community. Many …   Wikipedia

  • KISS principle — K.I.S.S. redirects here. seealso|WP:KISS. For other uses, see Kiss (disambiguation). The KISS principle (backronymed to Keep It Simple, Stupid ) states that design simplicity should be a key goal and unnecessary complexity avoided. It serves as a …   Wikipedia

  • You Ain't Gonna Need It — In software engineering, YAGNI, short for You Ain t Gonna Need It , suggests to programmers that they should not add functionality until it is necessary. Ron Jeffries writes, Always implement things when you actually need them, never when you… …   Wikipedia

  • Coding by exception — is an anti pattern where software quickly degrades in performance and maintainability because it evolves by having special case functionality added piecemeal. This typically happens because an existing piece of software is extended to cover… …   Wikipedia

  • Commercial off-the-shelf — In the United States, Commercially available Off The Shelf (COTS) is a Federal Acquisition Regulation (FAR) term defining a nondevelopmental item (NDI) of supply that is both commercial and sold in substantial quantities in the commercial… …   Wikipedia

  • BQM-147 Dragon — NOTOC Infobox Aircraft name=BQM 147 Dragon caption= type=Reconnaissance drone national origin=United States manufacturer=BAI Aerosystems designer= first flight= introduced= retired= status= primary user= more users= produced= number built=… …   Wikipedia

Share the article and excerpts

Direct link
Do a right-click on the link above
and select “Copy Link”